Re: [DMM] Mobility Exposure and Selection WT call

Alper Yegin <alper.yegin@yegin.org> Thu, 19 February 2015 15:35 UTC

Return-Path: <alper.yegin@yegin.org>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D5BE1A90F5 for <dmm@ietfa.amsl.com>; Thu, 19 Feb 2015 07:35:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehvt8J-lDC0v for <dmm@ietfa.amsl.com>; Thu, 19 Feb 2015 07:35:50 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC1DD1A90F6 for <dmm@ietf.org>; Thu, 19 Feb 2015 07:35:48 -0800 (PST)
Received: from [192.168.2.49] (88.247.135.202.static.ttnet.com.tr [88.247.135.202]) by mrelay.perfora.net (node=mreueus001) with ESMTP (Nemesis) id 0MBTkG-1YE3jo0r1K-00AVCy; Thu, 19 Feb 2015 16:30:30 +0100
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_4E995D64-9634-43EF-B12C-5CD80EAE7193"
From: Alper Yegin <alper.yegin@yegin.org>
In-Reply-To: <54E5A34C.2030106@gmail.com>
Date: Thu, 19 Feb 2015 17:30:23 +0200
Message-Id: <75DD1093-4761-4E0C-A5B9-1A1A96D850CE@yegin.org>
References: <A730EA79-F6CF-49CD-9933-9FDA4AA75541@yegin.org> <556A06B1-A71C-45DC-A5FB-66CC8ECF47B8@yegin.org> <223129BA-541E-4C56-9364-6C2B8A5A1D3B@yegin.org> <29DDE580-C9A3-4825-8C0B-CF6844438BEC@yegin.org> <54DB49BF.9090702@gmail.com> <4238F47D-1284-46D3-AF61-F173E4A3BDBE@yegin.org> <54E5A34C.2030106@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-Provags-ID: V02:K0:bSE7ylB4Oq4tCEgmoGjQJ8DUu7j+fz+/y1a1zX0L28b PZo+blX9a3jg2G42Fe4VZ/0j2hVORzOGTyB22Pw7iXM3EWPxvs qNvQoR/8nV16hJby52dOmwVhSnPXX8T15vE7ztMLEZnQErIsGm rCmObBeosiZ3SGVSYZiARYqb4sbW2ZFRvP+tpsrsNp2FK+1CjW 84S+DdouAX6a1KAY4lc/H8ztZaNU4LB/PDgCRJrZd/6SEksATb tbKqMlKy7qJBFuCivQM3a0VaRpnISpFFavb5/GJ3OTCWLq0NV7 TlxR8w4UkKUE2XvEl9coVUGW5l7UJgWKz63detP/JRi90Aem/d T95jZIYpUYBxVSLR3SN69Yu53ITokLlknAOk+N+LrnXPeEtNyY VsLCp65RP9Zww==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmm/HJKI0F1vNdGH1GCqfYzxPyLYx7Q>
Cc: dmm@ietf.org
Subject: Re: [DMM] Mobility Exposure and Selection WT call
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2015 15:35:54 -0000

>> 
>> This is source address selection, hence multicast address is out-of
>> picture. Unicast vs anycast distinction is orthogonal to mobility
>> type of the address.
>> 
>>> - MAC-based, random-based (RFC7217).
>> 
>> Orthogonal.
> 
> ?  One wouldn't want her 'fixed' address (not the 'sustained', not
> the 'nomadic') be a random-based address RFC7217.  That RFC's abstract says:
>> This document specifies a method for generating IPv6 Interface
>> Identifiers to be used with IPv6 Stateless Address Autoconfiguration
>> (SLAAC), such that an IPv6 address configured using this method is
>> stable within each subnet, but the corresponding Interface
>> Identifier changes when the host moves from one network to another.
> 
> 

When using the "fixed" IP address, the host stays connected to the same (logical/home) network at all times, anyways.
Hence, by the above definition, there's no reason to change the interface ID.

I don't know if it makes sense to request a fixed and random-based IP address. But if someone does it, it works.

Alper




>>> - configured by SLAAC, by DHCPv6, by PPP, or registered (RFC
>>> 6775).
>>> 
>> 
>> Orthogonal.
>> 
>> 
>>> E.g. a nomadic address could never be a link-local address.
>>> 
>>>> #2. Describe how IP address type information is conveyed from
>>>> network to MN.
>>> 
>>> If one designs a protocol to convey address type information from
>>> the network to the end node, then one could also add the other
>>> types mentioned above.
>>> 
>>> SLAAC could never 'convey' the address type to the end-node,
>>> because SLAAC is an operation happening with as heavy weight from
>>> the Server (router) as from the Client (Host): the Router decides
>>> the prefix but the Client decides the Interface ID.
>>> 
>> 
>> Still, the network can convey the type of IP address to the host.
>> Also, one can imagine augmenting Router Solicitation to let the host
>> convey its requested type.
> 
> I agree.
> 
> Alex
> 
> 
>>> Address Registration Option of 6lo and BTLE would have the Host
>>> conveying this information to the Router (and not vice-versa).
>>> 
>> 
>> OK.
>> 
>> Alper
>> 
>> 
>>> Yours,
>>> 
>>> Alex
>>> 
>>>> WT agreed to use draft-yegin-dmm-ondemand-mobility as the
>>>> baseline for item#1 (the API). A revision of the draft will also
>>>> include a new section to cover backward compatibility (Danny will
>>>> provide the draft text). Comments on the draft are welcome.
>>>> 
>>>> The next call will be about items #2/#3 (IP address
>>>> configuration enhancements associated with the API). We intend to
>>>> schedule that one in about 2 weeks.
>>>> 
>>>> Alper
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Feb 9, 2015, at 9:59 AM, Alper Yegin wrote:
>>>> 
>>>>> Folks,
>>>>> 
>>>>> See below for the Webex details. Remember, the call is on Tue,
>>>>> Feb 10, at 4pm CET. And don't forget to read the documents in
>>>>> the reading list prior to the call.
>>>>> 
>>>>>> Attendees _shall read _the following material before the call
>>>>>> so that we can directly jump to the discussions:
>>>>>> 
>>>>>> 1.
>>>>>> http://www.ietf.org/proceedings/91/slides/slides-91-dmm-4.pdf
>>>>>> 
>>>>>> 
> 2. http://www.ietf.org/proceedings/90/slides/slides-90-dmm-6.pdf
>>>>>> 3.
>>>>>> https://datatracker.ietf.org/doc/draft-yegin-dmm-ondemand-mobility/
>>>>>> 
>>>>>> 
> 4. http://www.ietf.org/proceedings/88/slides/slides-88-dmm-8.pdf
>>>>>> 5. http://tools.ietf.org/html/draft-liu-dmm-mobility-api-02
>>>>> 
>>>>> 
>>>>> 
>>>>> Alper
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> *DMM - Mobility Exposure and Selection WT* Tuesday 10 February
>>>>> 2015 16:00  |  Europe Time (Paris, GMT+01:00)  |  1 hr 30 min
>>>>> 
>>>>>> *Join WebEx meeting*
>>>>>> <https://ietf.webex.com/ietf/j.php?MTID=m1dad9871a277ff2ab142ae8ff4b77ad3>
>>>>>> 
>>>>>> 
>>>>>> 
> Meeting number:	641 085 326
>>>>>> Meeting password:	dmm1911
>>>>>> 
>>>>>> *Join by phone* *1-877-668-4493* Call-in toll free number
>>>>>> (US/Canada) *1-650-479-3208* Call-in toll number (US/Canada)
>>>>>> Access code: 641 085 326 Toll-free calling restrictions
>>>>>> <http://www.webex.com/pdf/tollfree_restrictions.pdf>
>>>>>> 
>>>>>> Add this meeting
>>>>>> <https://ietf.webex.com/ietf/j.php?MTID=m0855d524ccb7239248d0ce34e19f38c8>
>>>>>> to your calendar.
>>>>>> 
>>>>>> Can't join the meeting? Contact support.
>>>>>> <https://ietf.webex.com/ietf/mc>
>>>>>> 
>>>>>> IMPORTANT NOTICE: Please note that this WebEx service allows
>>>>>> audio and other information sent during the session to be
>>>>>> recorded, which may be discoverable in a legal matter. By
>>>>>> joining this session, you automatically consent to such
>>>>>> recordings. If you do not consent to being recorded, discuss
>>>>>> your concerns with the host or do not join the session.
>>>>>> 
>>>>> <WebEx_Meeting.ics>
>>>>> 
>>>>> 
>>>>> On Jan 27, 2015, at 11:12 AM, Alper Yegin wrote:
>>>>> 
>>>>>> Poll is closed, and majority selected the following date for
>>>>>> the call:
>>>>>> 
>>>>>> Feb 10, 4pm CET. 1,5hr call.
>>>>>> 
>>>>>> Please mark your calendars.
>>>>>> 
>>>>>> In this call, we'll aim making progress on the I-D for item#1
>>>>>> (an API for source address selection).
>>>>>> 
>>>>>> Attendees _shall read _the following material before the call
>>>>>> so that we can directly jump to the discussions:
>>>>>> 
>>>>>> 1.
>>>>>> http://www.ietf.org/proceedings/91/slides/slides-91-dmm-4.pdf
>>>>>> 
>>>>>> 
> 2. http://www.ietf.org/proceedings/90/slides/slides-90-dmm-6.pdf
>>>>>> 3.
>>>>>> https://datatracker.ietf.org/doc/draft-yegin-dmm-ondemand-mobility/
>>>>>> 
>>>>>> 
> 4. http://www.ietf.org/proceedings/88/slides/slides-88-dmm-8.pdf
>>>>>> 5. http://tools.ietf.org/html/draft-liu-dmm-mobility-api-02
>>>>>> 
>>>>>> 
>>>>>> Alper
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Jan 23, 2015, at 3:28 PM, Alper Yegin wrote:
>>>>>> 
>>>>>>> Folks,
>>>>>>> 
>>>>>>> Please mark your availability on the following doodle for
>>>>>>> our next DMM WG Mobility Exposure and Selection WT call:
>>>>>>> 
>>>>>>> http://doodle.com/7xgcr8x6cgxnbzur
>>>>>>> 
>>>>>>> Register your availability no later than the end of Monday
>>>>>>> (Jan 26).
>>>>>>> 
>>>>>>> Alper
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________ dmm mailing list
>>>> dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
>>>> 
>>> 
>>> 
>>> _______________________________________________ dmm mailing list
>>> dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
>> 
>> 
>> 
> 
>